Application Decision Process

This doc explains the process through which the applicant/application status is decided in Infinity Onboarding.

When an applicant submits the details after the identity verification, the Identity Verification component verifies the submitted details and passes its response by using its integration services. The response is then fetched by the Integration services of the Decision Engine.

The Decision Engine runs the response through the decision criteria of the applicant and co-applicant and provides the applicant status. The applicant and the co-applicant status is stored in the Journey Manager.

Similarly, when an application is submitted, the Decision Engine decides the application status based on the applicant's status. The applicant status in the Journey Manager is fetched by the Integration Services of the Decision Engine. The Decision Engine runs the applicant status through the decision criteria of application and provides the application status.

The decision criteria of the applicant and application must be created and uploaded to the database.

Infinity Onboarding

Currently, the Infinity Onboarding app uses IDology as the Identity Verification component and Open Rules Container as the Decision Engine.

Hence, IDology verifies the applicant details and its Integration services pass the response to the Object services of the Open Rules Container. The Open Rules Container maintains a Rule Engine to decide the applicant and application status.

The Rule Engine that is used to decide the status of main applicant and co-applicant contains the conditions such as PA_Lists, ID_Qualifiers, and ID_Results. The values of these conditions are passed as a response by IDology.

The Open Rules Container runs the IDology response through the Applicant Status Rule Engine and provides the status of the main applicant and co-applicant. The applicant status is then stored in the Journey Manager.

After submitting the application, the Object services of the Open Rules Container fetch the applicant status from the Journey Manager and runs it through the Rule Engine of the Application Status.

The Rule Engine that is used to decide the application status contains the possible values of the applicant’s and co-applicant’s status.

The default Rule Engines for the Applicant status and Application status in the Infinity Onboarding app are available in the dbstorage table of the dlp schema that is available in the Database used by Onboarding. These Rule Engine files are stored in the database in the form of Excel files.

Configuring the Rule Engine

You can configure the rule engine as per your requirements. To do so follow these steps.

1. Start the MySQL Workbench.
2. The existing connections are displayed when you click the MySQL Connection on the left navigation pane.
3. Open the required connection. In the case of the Infinity Onboarding app, it is dbxlendingqa.
4. From the Schemas section, go to dlp > dbstorage . The available files in the table are displayed.
5. Right-click the Content column of the required file and select Save Value To File from the list. The file is saved to your system.
6. Open the file, make the required changes, and save them.
7. Now, in the SQL Workbench, right-click the Content column of the file that you updated and select Load Value From File from the list.
8. Upload the updated file and replace the existing file.
9. After making the mentioned changes in the SQL Workbench, publish the Quantum Fabric app associated with Open Rules. In the case of Onboarding, it is dbxRuleService.

The rule engine file is usually available in the .xls format. You can download the sample files from here.

For more information about the Open Rules Container, click here.